-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: deprecate Parsing component and replace them in starter projects #6697
Conversation
CodSpeed Performance ReportMerging #6697 will degrade performances by 27.44%Comparing Summary
Benchmarks breakdown
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's better if we switch the legacy components for the new components in the starter projects
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
On testing found a bug in new parser component: data_to_text : test portfolio website generator. |
@Cristhianzl @erichare @mendonk Looking forward to your support for review. |
…clude legacy components in the test scenario 🔧 (decisionFlow.spec.ts): increase timeout from 500ms to 2000ms for better stability and reliability in waiting for selectors to appear
* commit '6c2ff92ccf083f038d9a97a749b4e0f30a60247a': (255 commits) docs: Update documentation and add TAVILY_API_KEY to environment variables (langflow-ai#7366) docs: mcp server component and integrations (langflow-ai#7286) docs: v1.3 (langflow-ai#7160) chore(deps-dev): bump vite from 5.4.14 to 5.4.16 in /src/frontend (langflow-ai#7365) fix: add secret key loading functionality to basic templates (langflow-ai#7363) docs: platform content (langflow-ai#7091) chore: bump langflow and langflow-base for 1.3.0 release (langflow-ai#7362) docs: ensure asset paths update on draft rebuilds (langflow-ai#7355) fix: Prevent API key banner from displaying when key is unavailable (langflow-ai#7356) fix: MCP SSE Model tool mode issue (langflow-ai#7360) feat: deprecate Parsing component and replace them in starter projects (langflow-ai#6697) fix: fixed the parser component (langflow-ai#7303) ref: split ast parsing / class exec loops (langflow-ai#7248) feat: Update AgentQL templates (langflow-ai#7165) feat: add a unified local vector store (langflow-ai#6995) fix: update currentflow to be fetched from Flow Store for icon to be rendered correctly (langflow-ai#7354) feat: expose serialization truncation constants in /config route (langflow-ai#7316) feat: lmprove MCP langflow port selection and error handling (langflow-ai#7327) fix: adds priority sorting for sidebar components and makes LanguageModel appear first (langflow-ai#7322) fix: make agent work with new tool mode backend updates (langflow-ai#7314) ... # Conflicts: # src/frontend/src/utils/styleUtils.ts 更新到V1.3.0
This pull request includes changes to mark certain components as legacy and format JSON files for better readability. The most important changes include setting the
legacy
attribute toTrue
for specific components and formatting theBlog Writer.json
file.Marking components as legacy:
src/backend/base/langflow/components/processing/parse_data.py
: Addedlegacy = True
to theParseDataComponent
class.src/backend/base/langflow/components/processing/parse_dataframe.py
: Addedlegacy = True
to theParseDataFrameComponent
class.Formatting JSON files:
src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json
: Reformatted the JSON structure to use arrays foroutput_types
,inputTypes
,field_order
, and other fields for better readability. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]